-
Notifications
You must be signed in to change notification settings - Fork 227
Moved to one SubgraphManifest schema file per protocol #821
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
evaporei
merged 2 commits into
graphprotocol:master
from
streamingfast:feature/schema-per-protocol
Feb 8, 2022
Merged
Moved to one SubgraphManifest schema file per protocol #821
evaporei
merged 2 commits into
graphprotocol:master
from
streamingfast:feature/schema-per-protocol
Feb 8, 2022
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
One remark I have is that I can easily see Cross-Chain subgraphs becoming a thing and then the manifest would be a mix of data sources from different protocol. |
evaporei
reviewed
Jan 28, 2022
evaporei
reviewed
Jan 28, 2022
evaporei
reviewed
Jan 28, 2022
evaporei
reviewed
Jan 28, 2022
evaporei
reviewed
Jan 28, 2022
Going to update all this today or tomorrow. |
PR updated. |
This will make it easier to add new network and will improve error messages when someone will be using fields that do not exist on a specific network but does in other (`temlates` for example used in NEAR were given a bunch of errors like the support was possible while it should have displayed an error on the `templates` node itself). Using `templates` on NEAR before this PR: ``` ✔ Apply migrations ✖ Failed to load subgraph from ../graph-node-dev/subgraphs/near/data-source/testnet.yaml: Error in ../graph-node-dev/subgraphs/near/data-source/testnet.yaml: Path: templates > 0 > source No value provided Path: templates > 0 > mapping Unexpected key in map: receiptHandlers Path: templates > 0 > mapping > abis No value provided ``` And with this PR: ``` $ ./bin/graph build ../graph-node-dev/subgraphs/near/data-source/testnet.yaml ✖ Failed to load subgraph from ../graph-node-dev/subgraphs/near/data-source/testnet.yaml: Error in ../graph-node-dev/subgraphs/near/data-source/testnet.yaml: Path: / Unexpected key in map: templates ```
8addafa
to
00427b7
Compare
evaporei
reviewed
Feb 8, 2022
@@ -9,6 +9,14 @@ describe('Validation', () => { | |||
exitCode: 1, | |||
}, | |||
) | |||
cliTest( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yaaay!! 🎉
evaporei
approved these changes
Feb 8, 2022
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This will make it easier to add new network and will improve error messages when someone will be using fields that do not exist on a specific network but does in other (
temlates
for example used in NEAR were given a bunch of errors like the support was possible while it should have displayed an error on thetemplates
node itself).Using
templates
on NEAR before this PR:And with this PR: